< previous page page_415 next page >

Page 415
To address your unique Internet development needs
To assist you when you need to access special kinds of persistent information not limited to relational data
To assist you in developing faster, smaller, and more efficient applications
The latest release of ADO is the standard for database access for Microsoft Visual Studio languages. ADO presents a common facade for developing one data access subsystem for either desktop or Internet deployment. ADO supports several different development needs, including the needs of the Graphical User Interface Subsystem and the Business Rule Subsystem, as well as packaged tools, programming languages, and browsers.
According to Microsoft, ADO will eventually be a superset of RDO. For now, it doesn't quite support every powerful feature of RDO. ADO is the object-based interface to OLE DB. By using a DAO-like data access interface, developers can now access an even broader variety of data sourcesusing both OLE DB service providers and existing ODBC drivers through its OLE DB for ODBC intermediate interface. ADO's most serious shortcoming at this point is its scope. ADO 1.5 implements only part of RDO's full range of functionality. Later versions will implement a superset of both RDO and DAO.
You'll find the key benefits of ADO to be ease of use, high speed, low memory overhead, and a small disk footprint. Among many usability and technical features, ADO supports certain critical features for building client/server and Web-based applications, including
Hierarchy-less data access objects. Unlike DAO or RDO, there's no hierarchy of objects to browse in order to create objects. That is, an ADO recordset object doesn't need a database object initialized first in order to access information from a database. This is very helpful when you have a recordset with a query that can be activated against two or more database servers.
Stored procedures that enable you to pass In and Out parameters, return values, and multiple recordsets.
Batch updating that helps improve performance by locally caching changes to data and then writing them all to the server in a single update.
Free-threaded objects for efficient Web server applications.
Different cursor types.
Support for limits on the number of returned rows.
Support for various query goals you can implement for performance tuning.

 
< previous page page_415 next page >

If you like this book, buy it!